-
Notifications
You must be signed in to change notification settings - Fork 36
Add support for JLink plugins #603
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: master
Are you sure you want to change the base?
Conversation
|
The tests are failing, because some of the introduced plugin options are not available with all JDK vendors. |
…endors and versions support this option
|
Hi @Til7701 -- you are right, CDS is a hotspot-specific thing, but other Java vendors like IBM may chose to replace hotspot and its CDS with something else -- like Eclipse OpenJ9 as Memory-Management and GC implementation with SCC (shared class cache) as an almost equivalent implementation. |
pom.xml
Outdated
| <!-- This test does not work for all jdk vendors and versions --> | ||
| <pomExclude>cli-options/generate-cds-archive/pom.xml</pomExclude> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can you move the exclusion into a profile?
The profile could get activated by the existence of the property openj9.compiler or if the property java.vm.vendor equals Eclipse OpenJ9 or if java.vendor equals IBM Corporation.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I added profiles for the exclusion. I had to create one for each, since Maven cannot activate a profile based on multiple properties.
|
OK, one more thing. The option The files you added (e.g. |
# Conflicts: # src/main/java/org/apache/maven/plugins/jlink/JLinkMojo.java
Fixes #602
Following this checklist to help us incorporate your
contribution quickly and easily:
for the change (usually before you start working on it). Trivial changes like typos do not
require a GitHub issue. Your pull request should address just this issue, without
pulling in other changes.
[#<num>] - Fixes bug in ApproximateQuantiles,where you replace
#<num>with the appropriate GitHub issue. Best practiceis to use the GitHub issue title in the pull request title and in the first line of the
commit message.
mvn clean verifyto make sure basic checks pass. A more thorough check willbe performed on your pull request automatically.
mvn -Prun-its clean verify).If your pull request is about ~20 lines of code you don't need to sign an
Individual Contributor License Agreement if you are unsure
please ask on the developers list.
To make clear that you license your contribution under
the Apache License Version 2.0, January 2004
you have to acknowledge this by using the following check-box.
I hereby declare this contribution to be licenced under the Apache License Version 2.0, January 2004
In any other case, please file an Apache Individual Contributor License Agreement.
Description
This PR add support for the JLink options
--generate-cds-archiveand--order-resources.Additionally, it adds the ability to supply additional args to JLink to support undocumented plugins. See #602 for a list of those.